Method and device for scheduling multi-flow transmission

ABSTRACT

The present application provides methods and apparatuses for scheduling multi-flow transmission. A method includes: receiving from a base station, a first MAC layer configuration parameter corresponding to a first MAC entity and a second MAC layer configuration parameter corresponding to a second MAC entity, each comprising a set of mapping and a MAC-layer related parameter corresponding to the set of mapping; executing the mapping corresponding to each MAC entity; and independently executing a MAC layer function based on the MAC layer-related parameter corresponding to each MAC entity. Embodiments of the present application can satisfy a demand of multi-flow transmission.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of a U.S. patent application Ser. No.14/554,460, filed on Nov. 26, 2014, which is a continuation ofInternational Application No. PCT/CN2012/076284, filed on May 30, 2012.All of the afore-mentioned patent applications are hereby incorporatedby reference in their entireties.

TECHNICAL FIELD

The present application relates to wireless communications technologies,and in particular, to a method and a device for scheduling multi-flowtransmission.

BACKGROUND

In a long term evolution (LTE) technology, device to device (D2D) oruplink (Uplink, UL) convergence, a UL cross-radio access technology(RAT) multi-carrier technology, a multi-flow transmission scenarioexists. In a multi-flow transmission scenario, a multi-flow controlmethod may be adopted to split different radio bearers (RB) to differentcells for data transmission. For example, a control plane bearer and auser plane bearer are transmitted in different cells separately, ordifferent RBs are mapped to different cells.

In the multi-flow transmission scenario, transmission resources ofdifferent cells need to be occupied, and therefore, logic channels needto be mapped to different transport channels and/or mapped to differentphysical entities. However, according to an existing Media AccessControl (MAC) layer function, all logic channels can only be mapped to asame transport channel and a same physical entity, and it cannot beimplemented that logic channels corresponding to different services aremapped to different transport channels and/or physical entities.

SUMMARY

The present application provides a method and a device for schedulingmulti-flow transmission, which are used to map different logic channelsto different transport channels and/or physical entities, so as toimprove MAC layer transmission efficiency.

One aspect of the present application provides a method for schedulingmulti-flow transmission, including:

receiving a MAC layer configuration parameter corresponding to a mediaaccess control MAC entity, where when there is one MAC entity, the MAClayer configuration parameter includes at least two sets of mappings,and the mapping includes a first mapping and/or a second mapping; orwhen there are at least two MAC entities, a MAC layer configurationparameter of each MAC entity includes a set of mapping, and the mappingincludes a third mapping and/or a fourth mapping; and

executing a MAC layer function according to the MAC layer configurationparameter, and performing MAC layer data transmission, where

the first mapping is a mapping between a logic channel/radio bearer RBand a transport channel;

the second mapping is a mapping between a transport channel and acell/physical entity;

the third mapping is a mapping between a logic channel/radio bearer RBand a transport channel/each MAC entity; and

the fourth mapping is a mapping between a transport channel/each MACentity and a cell/physical entity.

Another aspect of the application further provides a method forscheduling multi-flow transmission, including:

determining a MAC layer configuration parameter corresponding to a mediaaccess control MAC entity, where when there is one MAC entity, the MAClayer configuration parameter includes at least two sets of mappings,and the mapping includes a first mapping and/or a second mapping; orwhen there are at least two MAC entities, a MAC layer configurationparameter of each MAC entity includes a set of mapping, and the mappingincludes a third mapping and/or a fourth mapping; and

sending the MAC layer configuration parameter to a terminal, so that theterminal executes a MAC layer function according to the MAC layerconfiguration parameter, and performs MAC layer data transmission, where

the first mapping is a mapping between a logic channel/radio bearer RBand a transport channel;

the second mapping is a mapping between a transport channel and acell/physical entity;

the third mapping is a mapping between a logic channel/radio bearer RBand a transport channel/each MAC entity; and

the fourth mapping is a mapping between a transport channel/each MACentity and a cell/physical entity.

Another aspect of the present application further provides a device forscheduling multi-flow transmission, including:

a receiving module, configured to receive a MAC layer configurationparameter corresponding to a media access control MAC entity, where whenthere is one MAC entity, the MAC layer configuration parameter includesat least two sets of mappings, and the mapping includes a first mappingand/or a second mapping; or when there are at least two MAC entities, aMAC layer configuration parameter of each MAC entity includes a set ofmapping, and the mapping includes a third mapping and/or a fourthmapping, where the first mapping is a mapping between a logicchannel/radio bearer RB and a transport channel;

the second mapping is a mapping between a transport channel and acell/physical entity;

the third mapping is a mapping between a logic channel/radio bearer RBand a transport channel/each MAC entity; and

the fourth mapping is a mapping between a transport channel/each MACentity and a cell/physical entity; and

a processing module, configured to execute a MAC layer functionaccording to the MAC layer configuration parameter received by thereceiving module, and perform MAC layer data transmission.

Another aspect of the application further provides a device forscheduling multi-flow transmission, including:

a determining module, configured to determine a MAC layer configurationparameter corresponding to a media access control MAC entity, where whenthere is one MAC entity, the MAC layer configuration parameter includesat least two sets of mappings, and the mapping includes a first mappingand/or a second mapping; or when there are at least two MAC entities, aMAC layer configuration parameter of each MAC entity includes a set ofmapping, and the mapping includes a third mapping and/or a fourthmapping, where

the first mapping is a mapping between a logic channel/radio bearer RBand a transport channel;

the second mapping is a mapping between a transport channel and acell/physical entity;

the third mapping is a mapping between a logic channel/radio bearer RBand a transport channel/each MAC entity; and

the fourth mapping is a mapping between a transport channel/each MACentity and a cell/physical entity; and

a sending module, configured to send the MAC layer configurationparameter determined by the determining module to a terminal, so thatthe terminal executes a MAC layer function according to the MAC layerconfiguration parameter, and performs MAC layer data transmission.

It can be known from the foregoing technical solutions that a differencefrom the prior art in which all logic channels can only be mapped to asame transport channel and a same physical entity lies in that in thepresent embodiment of the application, by configuring at least two setsof mappings, multiple sets of mappings exist, so that different logicchannels/RBs can be mapped to different transport channels/MAC entitiesand/or cells/physical entities, so as to satisfy a demand of amulti-flow transmission scenario, thereby improving MAC layertransmission efficiency.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions in the embodiments of the presentapplication more clearly, the following briefly introduces theaccompanying drawings used in describing the embodiments. Apparently,the accompanying drawings in the following description show someembodiments of the present application, and persons of ordinary skill inthe art may still derive other drawings from these accompanying drawingswithout creative efforts.

FIG. 1 is a flow diagram of a method for scheduling multi-flowtransmission according to an embodiment of the present application;

FIG. 2 is a flow diagram of a method for scheduling multi-flowtransmission according to another embodiment of the present application;

FIG. 3 is a flow diagram of a method for scheduling multi-flowtransmission according to another embodiment of the present application;

FIG. 4 is a flow diagram of multi-flow transmission in the presentapplication;

FIG. 5 is another flow diagram of multi-flow transmission in the presentapplication;

FIG. 6 is a flow diagram of mapping of an uplink transport channel inthe present application;

FIG. 7 is a flow diagram of mapping of a downlink transport channel inthe present application;

FIG. 8 is a flow diagram of a method for scheduling multi-flowtransmission according to another embodiment of the present application;

FIG. 9 is a simplified block diagram of a device for schedulingmulti-flow transmission according to an embodiment of the presentapplication; and

FIG. 10 is a simplified block diagram of a device for schedulingmulti-flow transmission according to another embodiment of the presentapplication.

DETAILED DESCRIPTION

To make the objectives, technical solutions, and advantages of theembodiments of the present application more comprehensible, thefollowing clearly describes the technical solutions in the embodimentsof the present application with reference to the accompanying drawings.Apparently, the described embodiments are merely a part of theembodiments of the present application rather than all of theembodiments. All other embodiments obtained by persons of ordinary skillin the art based on the embodiments of the present application withoutcreative efforts shall fall within the protection scope of the presentapplication.

In a multi-flow transmission scenario, an LTE technology is used as anexample, and in this case, a network system includes a macro basestation, an access node, and a user device (UE). When a manner that acontrol plane bearer and a user plane bearer are transmitted indifferent cells is adopted, at an air interface, user plane data istransmitted through a link between the access node and the UE, andcontrol plane data is transmitted through a link between the macro basestation and the UE; and when a manner that different RBs are mapped todifferent cells is adopted, a link among the macro base station, theaccess node, and the UE is responsible for transmission of data on apart of the RBs, a link between the macro base station and the UE isresponsible for transmission of data on the other part of the RBs, wherethe RBs may be signaling radio bearers (SRB) bearing control plane dataor data radio bearers (DRB) bearing user plane data. In addition, in aD2D scenario, a D2D terminal (D2D UE) is equivalent to the access nodein the LTE, and in a UL convergence technology or UL cross-RATmulti-carrier technology scenario, a radio network controller (RNC) or anodeB is equivalent to the access node in the LTE technology.

A media access control (MAC) layer is located in a layer 2 (L2) protocolstack, the MAC layer is mainly responsible for scheduling of datatransmission, and a MAC layer function is executed by a MAC entity. Inthe prior art, each device, for example, a UE has only one MAC layerentity corresponding to one set of MAC layer configuration parameter.When a MAC layer function is executed, all logic channels are mapped toa same transport channel, where the logic channels include a dedicatedcontrol channel (DCCH), a dedicated traffic channel (DTCH), and a commoncontrol channel (CCCH), and the transport channel includes a downlinkshared channel (DL-SCH) and an uplink shared channel (UL-SCH); and thenare mapped to a same physical entity (Physical entity). FIG. 1 is a flowdiagram of a method for scheduling multi-flow transmission according toan embodiment of the present application, which includes:

Step 11: A terminal receives a MAC layer configuration parametercorresponding to a MAC entity, where when there is one MAC entity, theMAC layer configuration parameter includes at least two sets ofmappings, and the mapping includes a first mapping and/or a secondmapping; or when there are at least two MAC entities, a MAC layerconfiguration parameter of each MAC entity includes a set of mapping,and the mapping includes a third mapping and/or a fourth mapping, wherethe first mapping is a mapping between a logic channel/RB and atransport channel;

the second mapping is a mapping between a transport channel and acell/physical entity;

the third mapping is a mapping between a logic channel/radio bearer RBand a transport channel/each MAC entity; and

the fourth mapping is a mapping between a transport channel/each MACentity and a cell/physical entity.

Specifically, the first mapping includes:

a mapping between a logic channel identity and a transport channelidentity; or

a mapping between an RB identity and a transport channel identity;

the second mapping includes:

a mapping between a transport channel identity and a physical entityidentity; or

a mapping between a transport channel identity and a cell identity.

the third mapping includes:

a mapping between a logic channel identity and a transport channelidentity; or

a mapping between an RB identity and a transport channel identity; or

a mapping between an RB identity and each MAC entity identity; or

a mapping between a logic channel identity and each MAC entity identity;and

the fourth mapping includes:

a mapping between a transport channel identity and a cell identity; or

a mapping between each MAC entity identity and a cell identity; or

a mapping between a transport channel identity and a physical entityidentity; or

a mapping between each MAC entity identity and a physical entityidentity.

Step 12: The terminal executes a MAC layer function according to the MAClayer configuration parameter, and performs MAC layer data transmission.

In the embodiment of the present application, the terminal is, forexample, a UE, and in another system, the terminal may also have anothername, for example, a mobile station (MS).

In addition, in the embodiment of the present application, that a basestation sends a MAC layer configuration parameter is used as an example,and the base station may refer to an LTE base station (eNodeB), and inaddition, it may also that another device sends the MAC layerconfiguration parameter, for example, another LTE type access node, aD2D terminal, an RNC, or a NodeB. The another LTE type access node maybe, for example, a small base station (Pico), an indoor base station(Femto), a low mobility base station (LoMo), a local radio access point(AP), a low power node (LPN), or a radio remote unit (RRU).

Correspondingly, a base station side may execute a procedure as shown inFIG. 2, referring to FIG. 2, which includes:

Step 21: A base station determines a MAC layer configuration parametercorresponding to a MAC entity, where when there is one MAC entity, theMAC layer configuration parameter includes at least two sets ofmappings, and the mapping includes a first mapping and/or a secondmapping; or when there are at least two MAC entities, a MAC layerconfiguration parameter of each MAC entity includes a set of mapping,and the mapping includes a third mapping and/or a fourth mapping, where

the first mapping is a mapping between a logic channel/radio bearer RBand a transport channel;

the second mapping is a mapping between a transport channel and acell/physical entity;

the third mapping is a mapping between a logic channel/radio bearer RBand a transport channel/each MAC entity; and

the fourth mapping is a mapping between a transport channel/each MACentity and a cell/physical entity;

Step 22: The base station sends the MAC layer configuration parameter toa terminal, so that the terminal executes a MAC layer function accordingto the MAC layer configuration parameter, and performs MAC layer datatransmission.

In this embodiment, the base station (for example, eNodeB or NodeB) isused as an example, and an execution body may also be an LTE accessnode, a D2D terminal, an RNC, or the like.

The terminal may be an UE, an MS, or the like.

In the embodiment of the present application, in order to implement thatdifferent logic channels/RBs are mapped to different transportchannels/MAC entities and/or cells/physical entities, the foregoing atleast two sets of mappings need to be configured, each set of mappingcan complete mapping once, and therefore, through multiple sets ofmappings, the different logic channels/RBs can be mapped to thedifferent transport channels/MAC entities and/or cells/physicalentities. In this way, a demand of mapping different logic channels/RBsto different transport channels/MAC entities and/or cells/physicalentities during multi-flow transmission can be satisfied.

In order to implement at least two sets of mappings, the followingmanner may be adopted:

Manner 1: At least two MAC entities are configured, each MAC entitycorresponds to a set of MAC layer configuration parameter, and each setof MAC layer configuration parameter includes a set of mapping; or,

Manner 2: one MAC entity is configured, the MAC entity corresponds to atleast two sets of mappings, and in this case, the MAC layerconfiguration parameter corresponds to one MAC entity, but the MACentity corresponds to multiple sets of mappings.

Optionally, when there is one MAC entity, the at least two sets ofmappings are embodied in the form of a mapping list, and the mappinglist includes at least two sets of mapping identities.

In this case, the executing a MAC layer function according to the MAClayer configuration parameter includes:

executing the first mapping and the second mapping between channels atleast twice according to the MAC layer configuration parameter; or

executing the first mapping between channels at least twice according tothe MAC layer configuration parameter; or

executing the second mapping between channels at least twice accordingto the MAC layer configuration parameter; or

performing independent uplink scheduling according to the MAC layerconfiguration parameter.

Correspondingly, the first mapping between the channels includes:

when the first mapping is specifically a mapping between a logic channelidentity and a transport channel identity, mapping an uplink logicchannel to an uplink transport channel according to the mapping betweenthe logic channel identity and the transport channel identity; or

when the first mapping is specifically a mapping between an RB identityand a transport channel identity, mapping an uplink logic channel to anuplink transport channel according to the mapping between the RBidentity and the transport channel identity and correspondence betweenthe RB identity and a logic channel identity; or

when the first mapping is specifically a mapping between a logic channelidentity and a transport channel identity, mapping a downlink logicchannel to a downlink transport channel according to the mapping betweenthe logic channel identity and the transport channel identity; or

when the first mapping is specifically a mapping between an RB identityand a transport channel identity, mapping a downlink logic channel to adownlink transport channel according to the mapping between the RBidentity and the transport channel identity and correspondence betweenthe RB identity and a logic channel identity; and

the second mapping between the channels includes:

when the second mapping is specifically a mapping between a transportchannel identity and a physical entity identity, mapping, according tothe mapping between the transport channel identity and the physicalentity identity, an uplink transport channel to an uplink physicalchannel corresponding to a physical entity; or

when the second mapping is specifically a mapping between a transportchannel identity and a cell identity, mapping, according to the mappingbetween the transport channel identity and the cell identity, an uplinktransport channel to an uplink physical channel corresponding to a cell;or

when the second mapping is specifically a mapping between a transportchannel identity and a physical entity identity, mapping, according tothe mapping between the transport channel identity and the physicalentity identity, a downlink transport channel to a downlink physicalchannel corresponding to a physical entity; or

when the second mapping is specifically a mapping between a transportchannel identity and a cell identity, mapping, according to the mappingbetween the transport channel identity and the cell identity, a downlinktransport channel to a downlink physical channel corresponding to acell.

Optionally, when there are at least two MAC entities, the executing aMAC layer function according to the MAC layer configuration parameterincludes:

executing the third mapping and/or the fourth mapping between channelsaccording to the MAC layer configuration parameter, and performingindependent uplink scheduling.

Correspondingly, the third mapping between the channels includes:

when the third mapping is specifically a mapping between a logic channelidentity and a transport channel identity, mapping an uplink logicchannel to an uplink transport channel according to the mapping betweenthe logic channel identity and the transport channel identity; or

when the third mapping is specifically a mapping between an RB identityand a transport channel identity, mapping an uplink logic channel to anuplink transport channel according to the mapping between the RBidentity and the transport channel identity and correspondence betweenthe RB identity and a logic channel identity; or

when the third mapping is specifically a mapping between a logic channelidentity and a MAC entity identity, mapping, according to the mappingbetween the logic channel identity and the MAC entity identity, anuplink logic channel to an uplink transport channel corresponding to aMAC entity; or

when the third mapping is specifically a mapping between an RB identityand a MAC entity identity, mapping, according to the mapping between theRB identity and the MAC entity identity and correspondence between theRB identity and a logic channel identity, an uplink logic channel to anuplink transport channel corresponding to a MAC entity; or

when the third mapping is specifically a mapping between a logic channelidentity and a transport channel identity, mapping a downlink logicchannel to a downlink transport channel according to the mapping betweenthe logic channel identity and the transport channel identity; or

when the third mapping is specifically a mapping between an RB identityand a transport channel identity, mapping a downlink logic channel to adownlink transport channel according to the mapping between the RBidentity and the transport channel identity and correspondence betweenthe RB identity and a logic channel identity; or

when the third mapping is specifically a mapping between a logic channelidentity and a MAC entity identity, mapping, according to the mappingbetween the logic channel identity and the MAC entity identity, adownlink logic channel to a downlink transport channel corresponding toa MAC entity; or

when the third mapping is specifically a mapping between an RB identityand a MAC entity identity, mapping, according to the mapping between theRB identity and the MAC entity identity and correspondence between theRB identity and a logic channel identity, a downlink logic channel to adownlink transport channel corresponding to a MAC entity; and

the fourth mapping between the channels includes:

when the fourth mapping is specifically a mapping between a transportchannel identity and a physical entity identity, mapping, according tothe mapping between the transport channel identity and the physicalentity identity, an uplink transport channel to an uplink physicalchannel corresponding to a physical entity; or

when the fourth mapping is specifically a mapping between a transportchannel identity and a cell identity, mapping, according to the mappingbetween the transport channel identity and the cell identity, an uplinktransport channel to an uplink physical channel corresponding to a cell;or

when the fourth mapping is specifically a mapping between a MAC entityidentity and a physical entity identity, mapping, according to themapping between the MAC entity identity and the physical entityidentity, an uplink transport channel corresponding to a MAC entity toan uplink physical channel corresponding to a physical entity; or

when the fourth mapping is specifically a mapping between a MAC entityidentity and a cell identity, mapping, according to the mapping betweenthe MAC entity identity and the cell identity, an uplink transportchannel corresponding to a MAC entity to an uplink physical channelcorresponding to a cell; or

when the fourth mapping is specifically a mapping between a transportchannel identity and a physical entity identity, mapping, according tothe mapping between the transport channel identity and the physicalentity identity, a downlink transport channel to a downlink physicalchannel corresponding to a physical entity; or

when the fourth mapping is specifically a mapping between a transportchannel identity and a cell identity, mapping, according to the mappingbetween the transport channel identity and the cell identity, an uplinktransport channel to an uplink physical channel corresponding to a cell;or when the fourth mapping is specifically a mapping between a MACentity identity and a physical entity identity, mapping, according tothe mapping between the MAC entity identity and the physical entityidentity, a downlink transport channel corresponding to a MAC entity toa downlink physical channel corresponding to a physical entity; or

when the fourth mapping is specifically a mapping between a MAC entityidentity and a cell identity, mapping, according to the mapping betweenthe MAC entity identity and the cell identity, a downlink transportchannel corresponding to a MAC entity to a downlink physical channelcorresponding to a cell.

In addition, the correspondence between the RB identity and the logicchannel identity in the foregoing procedure may be determined when aradio bearer is configured. When a radio bearer is configured, the basestation sends correspondence between an RB identity and a logic channelidentity to a UE.

Optionally, the performing independent uplink scheduling according tothe MAC layer configuration parameter includes:

when there is one MAC entity and when new data transmission isperformed, scheduling, according to the first mapping and the secondmapping, uplink data of a logic channel that is mapped to a physicalentity/cell corresponding to an uplink grant resource; or

when there are at least two MAC entities and when new data transmissionis performed, scheduling, according to the third mapping and the fourthmapping, uplink data of a logic channel that is mapped to a physicalentity/cell corresponding to an uplink grant resource.

A specific scheduling method may include:

First, according to logic channel priorities and a sequence from high tolow of the logic channel priorities, a resource is allocated to a logicchannel which is mapped to the physical entity/cell corresponding to theuplink grant resource and on which a data amount that is greater thanzero is allowed to be transmitted.

A resource allocating method is that: The UE allocates a resource todata of a logic channel with a highest priority for uplink transmission.Only when an allowed transmitted data amount of the logic channel withthe highest priority is smaller than or equal to zero, the UE allocatesa remaining resource to a logic channel with a low priority for datatransmission.

Then, the UE subtracts a data amount that has been transmitted from theallowed transmitted data amount of the logic channel.

Next, when allowed transmitted data amounts of all logic channels thatare mapped to the physical entity/cell corresponding to the uplink grantresource is smaller than or equal to zero, and there is still aremaining uplink transmission resource, the UE allocates, according tothe sequence from high to low of the logic channel priorities, an uplinkresource to the logic channels that are mapped to the physicalentity/cell corresponding to the uplink grant resource. The UE allocatesa resource to the data of the logic channel with the highest priorityfor uplink transmission. Only when all logic channels with highpriorities are transmitted completely, the UE allocates a remainingresource to the logic channel with the low priority for datatransmission. When the UE completes data transmission of all the logicchannels, or uses up the uplink transmission resource, the UE endsuplink scheduling.

Optionally, the MAC layer configuration parameter further includes a MAClayer-related parameter corresponding to each set of mapping, and theMAC layer-related parameter includes at least one of the followingitems: a discontinuous reception (DRX) configuration parameter, asemi-persistent schedule (SPS) configuration parameter, and hybridautomatic repeat request (HARQ) retransmission times.

Optionally, the method may further include:

When there is one MAC entity, independently executing at least one MACfunction of the following items: DRX, SPS, and HARQ according to the MAClayer-related parameter corresponding to each set of mapping and usingeach set of mapping as a unit.

When there are at least two MAC entities, independently executing atleast one MAC function of the following items: DRX, SPS, and HARQaccording to the MAC layer-related parameter corresponding to each MACentity and using each MAC entity as a unit.

Optionally, the MAC layer configuration parameter may be carried inaddition, deletion, or reconfiguration dedicated signaling, afterreceiving the dedicated signaling, corresponding to Manner 1, the UEadds, deletes, or re-configures a MAC entity, and then performsdifferent mapping by adopting a different MAC entity, and correspondingto Manner 2, the UE adds, deletes, or re-configures a mapping, and thenperforms different mapping by adopting a different mapping.

In addition, optionally, the base station may also execute acorresponding MAC function at the base station side according to the MAClayer configuration parameter. The MAC layer function executed by thebase station corresponds to the MAC layer function executed by the UE,for example, during uplink data transmission, the UE maps an uplinklogic channel to an uplink transport channel, maps the uplink transportchannel to an uplink physical layer channel, and completes scheduling ofuplink data, and the base station maps an uplink physical layer channelto an uplink transport channel, maps the uplink transport channel to anuplink logic channel, and completes scheduling of downlink data.

Optionally, the MAC layer configuration parameter configured by the basestation may correspond to different MAC entities, or correspond to onlyone MAC entity but correspond to multiple sets of mappings, and forspecific content, reference may be made to the foregoing description ofthe UE side.

In this embodiment, by configuring at least two sets of mappings,different logic channels/RBs can be mapped to different transportchannels/MAC entities and/or cells/physical entities according todifferent sets of mappings, so as to satisfy a demand of a multi-flowtransmission scenario, thereby improving MAC layer transmissionefficiency.

In the following, that in an LTE scenario, an access node is an LPN isused as an example to describe a method in the embodiment of the presentapplication.

FIG. 3 is a flow diagram of a method for scheduling multi-flowtransmission according to another embodiment of the present application,where in this embodiment, that multiple MAC entities are configured isused as an example, and referring to FIG. 3, the method includes:

Step 31: A base station configures, according to a flow splittingpolicy, at least two MAC entities and a MAC layer configurationparameter that corresponds to each MAC entity for a UE.

The flow splitting policy may be that user plane data and control planedata are separately transmitted, and in this case, referring to FIG. 4,SRB data is transmitted in a macro cell (LTE eNB), and DRB data istransmitted in an LPN cell.

Alternatively, the flow splitting policy may be that RB data with asmall data amount and/or a high quality of service (QoS) demand istransmitted in a macro cell, and RB data with a great data amount and/ora low QoS demand is transmitted in an LPN cell, for example, referringto FIG. 5, SRB0 data, SRB1 data, and VoIP data are transmitted in themacro cell, and file transfer protocol (FTP) data is transmitted in theLPN cell.

The number of configured MAC entities may be the same as the number ofsplit data flows, for example, when split flows as shown in FIG. 4 orFIG. 5 are transmitted in the macro cell and the LPN cell, two MACentities may be configured, which are respectively configured to bemapped to the macro cell and the LPN cell.

Specifically, the MAC layer configuration parameter corresponding toeach MAC entity may be determined according to a specific flow splittingpolicy, for example, when an SRB0 and an SRB1 are transmitted in themacro cell and an SRB2 is transmitted in the LPN cell, if logic channelscorresponding to the SRB0, the SRB1, and the SRB2 are respectively aCCCH, and DCCHs with logic channel identities being 1 and 2, which arerepresented as a DCCH1 and a DCCH2 in the following, the CCCH and theDCCH1 are mapped to a transport channel of the macro cell, and the DCCH2is mapped to a transport channel of the LPN cell, in uplink, thetransport channel is an uplink shared channel (UL-SCH), and in downlink,the transport channel is a downlink shared channel (DL-SCH).

In this embodiment, multiple MAC entities are configured and each MACentity corresponds to one set of MAC layer configuration parameter. Eachset of MAC layer configuration parameter may include at least one of thefollowing items:

(1) MAC entity identity, used to identify a MAC entity of a UE andfacilitate addition/deletion/re-configuration of the MAC entity. Theidentity may be an integer (INTEGER) type. For example,

MAC-Entity-identity INTEGER (0 . . . X),

(2) Mapping between a MAC entity/transport channel and a cell/physical(PHY) entity. The mapping indicates that a MAC entity transport channelis mapped to a physical layer channel of the cell/PHY entity, and isused to represent a mapping between the transport channel and thephysical layer channel. For example:

The MAC entity is used as an example, and a mapping with the cell or thephysical entity may be respectively represented as follows:

MAC-Entity-mapping-with-cell Cell-identity

or MAC-Entity-mapping-with-PHY-entity PHY-entity-identity

“MAC-Entity-mapping-with-cell Cell-identity” is used as an example,usually an information unit is formed by a name and a type, where“MAC-Entity-mapping-with-cell” in the front represents a name, and“Cell-identity” in the rear represents a type, that is, a identity of aspecific cell to which the MAC entity (may be represented by using theMAC entity identity in the front) is mapped. For a subsequent similarexpressed specific meaning, reference may be made to the descriptionherein.

Cell-identity may be any kind of cell identity, for example, a physicalcell identity (PCI), a unique cell identity in a public land mobilenetwork (PLMN) range, an evolved-UMTS terrestrial radio access (EUTRA)cell global identifier (ECGI), a PCI and carrier frequency pointinformation, or a cell index number. The cell index number may be acurrently configured cell index (cellindex). The index information mayindex all configured cells. A PHY entity identity (PHY-entity-identity)is an identity uniquely identifying the PHY entity, and the identity maybe an INTEGER type.

(3) Mapping between a MAC entity/transport channel and a logicchannel/RB. The mapping indicates that the logic channel/RB is mapped tothe MAC entity, and is used to represent a mapping between the transportchannel and the logic channel. For example:

Logical-and-transport-mappingList ::= SEQUENCE SIZE(1..maxLogicalChannelNum)) OF Logical-and-transport-mappingLogical-and-transport-mapping ::= SEQUENCE { logicalChannelIdentitylogicalChannelIdentity  }

The foregoing content is also a specific expressing manner used todescribe the mapping between the logic channel and the transportchannel, for example, the number of logic channels mapped to the MACentity indicated by the foregoing MAC entity identity ismaxLogicalChannelNum, each logic channel may be specifically representedas “logicalChannelIdentity logicalChannelIdentity”, where“logicalChannelIdentity” in the front represents a name, that is,content to be described; and “logicalChannelIdentity” in the rearrepresents a type, that is, a specific logic channel identity. For asubsequent similar expressed specific meaning, reference may be made tothe description herein.

An RB identity (srb-Identity/drb-identity) may also be used to replacethe logic channel identity to represent the mapping.

Logical-and-RB-mappingList ::= SEQUENCE SIZE (1..maxRBNum))OF Logical-and-RB-mapping Logical-and-RB-mapping ::=  SEQUENCE {RB-identity RB-identity  }

(4) MAC-related parameter

The MAC parameter may include all or a part of MAC layer configurationparameters, for example, a DRX mechanism parameter, an HARQ maximumretransmission times (maxHARQ-Tx), and an SPS configuration parameter.

Step 32: The base station sends a dedicated signaling to the UE, wherethe dedicated signaling includes a manner for processing a MAC entityand a MAC layer configuration parameter corresponding to the MAC entity.

The processing manner may be to add, delete, or re-configure one ormultiple MAC entities, and a MAC layer configuration parametercorresponding to the added, deleted, or modified MAC entity is the MAClayer configuration parameter included in the dedicated signaling.

Particularly, a dedicated signaling used to delete a MAC layerconfiguration parameter may include only deleting a MAC entity identity(MAC-Entity-identity).

Step 33: The UE processes a corresponding MAC entity according to thededicated signaling.

According to an indication of the dedicated signaling, the MAC entitymay be added, deleted, or re-configured, which may be completedaccording to the MAC layer configuration parameter corresponding to eachMAC entity during specific configuration.

Step 34: The UE executes a MAC function separately according to a MAClayer configuration parameter corresponding to each processed MACentity.

After multiple MAC entities are configured, these MAC entitiesindependently execute a MAC layer function, and a MAC function executedby each MAC entity may include at least one of the following items:

(1) Uplink Transport Channel Mapping

Referring to FIG. 6, the MAC entity maps an uplink logic channel to acorresponding uplink transport channel according to a mapping(Logical-and-transport-mappingList/Logical-and-RB-mappingList) between aMAC entity/transport channel and a logic channel/RB in the correspondingMAC layer configuration parameter.

(2) Downlink Transport Channel Mapping

Referring to FIG. 7, the MAC entity maps a downlink logic channel to acorresponding downlink transport channel according to a mapping(Logical-and-transport-mappingList/Logical-and-RB-mappingList) between aMAC entity/transport channel and a logic channel/RB in the correspondingMAC layer configuration parameter.

(3) Uplink Physical Layer Channel Mapping

The MAC entity maps an uplink transport channel to an uplink physicallayer channel according to a mapping between a MAC entity/transportchannel and a cell/PHY entity in the corresponding MAC layerconfiguration parameter. Particularly, one MAC entity may be mapped toone or multiple cells/physical entities. For example, a MAC entity 1(that is, the MAC-Entity-identity is 1) is mapped to cells with a cellindex 1 and a cell index 2. In this case, a UL-SCH corresponding to theMAC entity 1 may be mapped to a physical uplink control channel (PUCCH)and a physical uplink shared channel (PUSCH) of the cell whose indexis 1. A DL-SCH corresponding to the MAC entity 1 may be mapped to aphysical downlink control channel (PDCCH) and a physical downlink sharedchannel (PDSCH) of the cell whose index is 1.

(4) Downlink Physical Layer Channel Mapping

The MAC entity maps a downlink transport channel to a downlink physicallayer channel according to a mapping between a MAC entity/transportchannel and a cell/PHY entity in the corresponding MAC layerconfiguration parameter. Particularly, one MAC entity may be mapped toone or multiple cells/physical entities. For example, a MAC entity 1(that is, the MAC-Entity-identity is 1) is mapped to cells with a cellindex 1 and a cell index 2. In this case, a DL-SCH corresponding to theMAC entity 1 may be mapped to a PDCCH and a PDSCH of the cell whoseindex is 1.

(5) Uplink Scheduling Based on a Logic Channel Priority

In the prior art, all logic channels are mapped to a same MAC entity,and therefore, during scheduling, priority sequencing and scheduling areperformed on all the logic channels. However, in this embodiment, logicchannels are mapped to different MAC entities, and therefore, for eachMAC entity, priority sequencing and scheduling are performed only on alogic channel mapped to the MAC entity itself. An independent executionrelationship exists between MAC entities. That is to say, when receivingan uplink grant (UL Grant) for new data transmission, the UE performsuplink scheduling according to a priority of a logic channel mapped to aMAC entity corresponding to an uplink grant sending cell/physical entityand according to a token bucket algorithm.

Specifically, for each MAC entity, when executing new data transmission,the UE allocates, according to a priority of a logic channel mapped tothe MAC entity, an uplink transmission resource by adopting a tokenbucket algorithm. The token bucket algorithm is a typical mathematicalalgorithm. Specific content of the token bucket algorithm includes: TheUE schedules, according to a sequence from high to low of logic channelpriorities, data of a logic channel which is mapped to the MAC entityand on which a currently allowed transmitted data amount (Bj)>0; andwhen Bj of all logic channels mapped to the MAC entity <=0, but there isstill a remaining uplink resource, the UE schedules, according to thesequence from high to low of the logic channel priorities, the data ofthe logic channel that is mapped to the MAC entity.

In this embodiment, by configuring multiple MAC entities for a UE, eachMAC entity corresponds to one set of mapping, so that multiple sets ofmappings can be configured, and different logic channels can be mappedto different transport channels and/or physical layer channels accordingto the multiple sets of mappings, so as to satisfy a demand of amulti-flow transmission scenario, thereby improving MAC layertransmission efficiency.

FIG. 8 is a schematic flowchart of a method for scheduling multi-flowtransmission according to another embodiment of the present application,where in this embodiment, that one MAC entity is configured but multiplesets of mappings are configured is used as an example, and referring toFIG. 8, the method includes:

Step 81: A base station configures, according to a flow splittingpolicy, one MAC entity and a MAC layer configuration parameter thatcorresponds to the MAC entity for a UE, where the MAC layerconfiguration parameter includes a mapping list, the mapping listincludes at least two sets of mapping parameters, and each set ofmapping parameter includes at least a set of mapping.

Being similar to the foregoing embodiment, according to the flowsplitting policy, it is assumed that data to be transmitted may beclassified into first data and second data, the first data istransmitted in a first cell, and the second data is transmitted in asecond cell, and the configured mapping may include: A logic channelcorresponding to the first data is mapped to a transport channel and/orphysical layer channel corresponding to the first cell, and a logicchannel corresponding to the second data is mapped to a transportchannel and/or physical layer channel corresponding to the second cell.

Each set of mapping parameter may include at least one of the followingitems:

(1) Mapping identity (Channel-Mapping-identity), used to identify amapping and facilitate addition/deletion/re-configuration of themapping. The identity may be an INTEGER type. For example,

Channel-Mapping-identity INTEGER (0 . . . X),

(2) Transport channel identity (Transport-Channel-identity), used toidentify a transport channel. The identity may be an INTEGER type. Forexample,

Transport-Channel-identity INTEGER (0 . . . X),

(3) Mapping between a transport channel and a cell/PHY entity. Themapping indicates that a MAC transport channel is mapped to a physicallayer channel of the cell/PHY entity. For example:

Transport-channel-mapping-with-cell Cell-identity

or

Transport-channel-mapping-with-PHY-entity PHY-entity-identity

Cell-identity may be any kind of cell identity, for example, a PCI, aunique cell identity in a PLMN range, an ECGI, a physical cell identityand carrier frequency point information, or a cell index number. Thecell index number may be a currently configured cell index (cellindex).The index information may index all configured cells. A PHY entityidentity (PHY-entity-identity) is an identity uniquely identifying thePHY entity, and the identity may be an INTEGER type.

(4) Mapping between a transport channel and a logic channel/RB. Themapping indicates that the logic channel/RB is mapped to the MAC entity.For example:

Logical-and-transport-mappingList ::= SEQUENCE SIZE(1..maxLogicalChannelNum)) OF Logical-and-transport-mapping Logical-and-transport-mapping ::= SEQUENCE { logicalChannelIdentity logicalChannelIdentity  }

An RB identity (srb-Identity/drb-identity) may also be used to replacethe logic channel identity to represent the mapping.

Logical-and-RB-mappingList ::= SEQUENCE SIZE(1..maxRBNum)) OF  Logical-and-RB-mapping Logical-and-RB-mapping::= SEQUENCE { RB-identity RB-identity  }

Particularly, deletion of a mapping information list may include onlydeleting a mapping identity (Channel-Mapping-identity).

(4) MAC-related parameter

The MAC parameter included in the mapping may include all or a part ofMAC layer configuration parameters, for example, a DRX mechanismparameter, an HARQ maximum retransmission times (maxHARQ-Tx), and an SPSconfiguration parameter.

Step 82: The base station sends a dedicated signaling to the UE, wherethe dedicated signaling includes the MAC layer configuration parameterand a corresponding processing manner.

The processing manner may be to add, delete, or re-configure one ormultiple mapping parameters.

Step 83: The UE processes a corresponding mapping parameter according tothe dedicated signaling.

According to an indication of the dedicated signaling, the mappingparameter may be added, deleted, or re-configured. A processed mappingparameter is the mapping parameter included in the dedicated signaling.

Step 84: The UE executes a MAC function according to each processedmapping parameter.

A MAC function executed by the MAC entity may include at least one ofthe following items:

(1) Uplink Transport Channel Mapping

The MAC entity maps an uplink logic channel to a corresponding uplinktransport channel according to a mapping(Logical-and-transport-mappingList) between a transport channel and alogic channel/RB. For a manner of mapping the uplink logic channel tothe uplink transport channel, reference may be made to FIG. 6.

(2) Downlink Transport Channel Mapping

The MAC entity maps a downlink logic channel to a corresponding downlinktransport channel according to a mapping(Logical-and-transport-mappingList) between a transport channel and alogic channel/RB. For a manner of mapping the downlink logic channel tothe downlink transport channel, reference may be made to FIG. 7.

(3) Uplink Physical Layer Channel Mapping

The MAC entity maps an uplink transport channel to an uplink physicallayer channel of a corresponding cell/physical entity according to amapping between a transport channel and a cell/PHY entity. Particularly,one MAC entity may be mapped to one or multiple cells/physical entities.

(4) Downlink Physical Layer Channel Mapping

The MAC entity maps a downlink transport channel to a downlink physicallayer channel of a corresponding cell/physical entity according to amapping between a transport channel and a cell/PHY entity. Particularly,one MAC entity may be mapped to one or multiple cells/physical entities.

(5) Uplink Scheduling Based on a Logic Channel Priority

In the prior art, all logic channels are mapped to a same transportchannel/physical entity/cell, and therefore, during scheduling, prioritysequencing and scheduling are performed on all the logic channels.

However, in this embodiment, logic channels are mapped to differenttransport channels/physical entities/cells, and therefore, for eachtransport channel/physical entity/cell, priority sequencing andscheduling are performed on a logic channel mapped to transportchannel/physical entity/cell itself.

Specifically, for each transport channel/physical entity/cell, whenexecuting new data transmission, the UE allocates, according to apriority of a logic channel mapped to the transport channel/physicalentity/cell, an uplink transmission resource by adopting a token bucketalgorithm. That is, the UE schedules, according to a sequence from highto low of logic channel priorities, data of a logic channel which ismapped to the transport channel/physical entity/cell and on which acurrently allowed transmitted data amount (Bj)>0; and when Bj of alllogic channels mapped to the transport channel/physical entity/cell <=0,but there is still a remaining uplink resource, the UE schedules,according to the sequence from high to low of the logic channelpriorities, the data of the logic channel that is mapped to thetransport channel/physical entity/cell.

In this embodiment, by configuring multiple sets of mappings for a UE,different logic channels can be mapped to different transport channelsand/or physical layer channels according to the multiple sets ofmappings, so as to satisfy a demand of a multi-flow transmissionscenario, thereby improving MAC layer transmission efficiency.

FIG. 9 is a schematic structural diagram of a device for schedulingmulti-flow transmission according to an embodiment of the presentapplication. The device may be a terminal, for example, a UE or an MS,and the device includes a receiving module 91 and a processing module92, where

the receiving module 91 is configured to receive a MAC layerconfiguration parameter corresponding to a MAC entity, where when thereis one MAC entity, the MAC layer configuration parameter includes atleast two sets of mappings, and the mapping includes a first mappingand/or a second mapping; or when there are at least two MAC entities, aMAC layer configuration parameter of each MAC entity includes a set ofmapping, and the mapping includes a third mapping and/or a fourthmapping, where the first mapping is a mapping between a logicchannel/radio bearer RB and a transport channel;

the second mapping is a mapping between a transport channel and acell/physical entity;

the third mapping is a mapping between a logic channel/radio bearer RBand a transport channel/each MAC entity; and

the fourth mapping is a mapping between a transport channel/each MACentity and a cell/physical entity; and

the processing module 92 is configured to execute a MAC layer functionaccording to the MAC layer configuration parameter, and perform MAClayer data transmission.

Optionally, the processing module is specifically configured to, whenthere is one MAC entity:

execute the first mapping and the second mapping between channels atleast twice according to the MAC layer configuration parameter; or

execute the first mapping between channels at least twice according tothe MAC layer configuration parameter; or

execute the second mapping between channels at least twice according tothe MAC layer configuration parameter; or

perform independent uplink scheduling according to the MAC layerconfiguration parameter.

Optionally, the processing module is specifically configured to performthe first mapping between the channels as follows:

when the first mapping is specifically a mapping between a logic channelidentity and a transport channel identity, mapping an uplink logicchannel to an uplink transport channel according to the mapping betweenthe logic channel identity and the transport channel identity; or

when the first mapping is specifically a mapping between an RB identityand a transport channel identity, mapping an uplink logic channel to anuplink transport channel according to the mapping between the RBidentity and the transport channel identity and correspondence betweenthe RB identity and a logic channel identity; or

when the first mapping is specifically a mapping between a logic channelidentity and a transport channel identity, mapping a downlink logicchannel to a downlink transport channel according to the mapping betweenthe logic channel identity and the transport channel identity; or

when the first mapping is specifically a mapping between an RB identityand a transport channel identity, mapping a downlink logic channel to adownlink transport channel according to the mapping between the RBidentity and the transport channel identity and correspondence betweenthe RB identity and a logic channel identity; and

perform the second mapping between the channels as follows:

when the second mapping is specifically a mapping between a transportchannel identity and a physical entity identity, mapping, according tothe mapping between the transport channel identity and the physicalentity identity, an uplink transport channel to an uplink physicalchannel corresponding to a physical entity; or

when the second mapping is specifically a mapping between a transportchannel identity and a cell identity, mapping, according to the mappingbetween the transport channel identity and the cell identity, an uplinktransport channel to an uplink physical channel corresponding to a cell;or

when the second mapping is specifically a mapping between a transportchannel identity and a physical entity identity, mapping, according tothe mapping between the transport channel identity and the physicalentity identity, a downlink transport channel to a downlink physicalchannel corresponding to a physical entity; or

when the second mapping is specifically a mapping between a transportchannel identity and a cell identity, mapping, according to the mappingbetween the transport channel identity and the cell identity, a downlinktransport channel to a downlink physical channel corresponding to acell.

Optionally, the processing module is specifically configured to, whenthere are at least two MAC entities:

execute the third mapping and/or the fourth mapping between channelsaccording to the MAC layer configuration parameter, and performindependent uplink scheduling.

Optionally, the processing module is specifically configured to performthe third mapping between the channels as follows:

when the third mapping is specifically a mapping between a logic channelidentity and a transport channel identity, mapping an uplink logicchannel to an uplink transport channel according to the mapping betweenthe logic channel identity and the transport channel identity; or

when the third mapping is specifically a mapping between an RB identityand a transport channel identity, mapping an uplink logic channel to anuplink transport channel according to the mapping between the RBidentity and the transport channel identity and correspondence betweenthe RB identity and a logic channel identity; or

when the third mapping is specifically a mapping between a logic channelidentity and a MAC entity identity, mapping, according to the mappingbetween the logic channel identity and the MAC entity identity, anuplink logic channel to an uplink transport channel corresponding to aMAC entity; or

when the third mapping is specifically a mapping between an RB identityand a MAC entity identity, mapping, according to the mapping between theRB identity and the MAC entity identity and correspondence between theRB identity and a logic channel identity, an uplink logic channel to anuplink transport channel corresponding to a MAC entity; or

when the third mapping is specifically a mapping between a logic channelidentity and a transport channel identity, mapping a downlink logicchannel to a downlink transport channel according to the mapping betweenthe logic channel identity and the transport channel identity; or

when the third mapping is specifically a mapping between an RB identityand a transport channel identity, mapping a downlink logic channel to adownlink transport channel according to the mapping between the RBidentity and the transport channel identity and correspondence betweenthe RB identity and a logic channel identity; or

when the third mapping is specifically a mapping between a logic channelidentity and a MAC entity identity, mapping, according to the mappingbetween the logic channel identity and the MAC entity identity, adownlink logic channel to a downlink transport channel corresponding toa MAC entity; or

when the third mapping is specifically a mapping between an RB identityand a MAC entity identity, mapping, according to the mapping between theRB identity and the MAC entity identity and correspondence between theRB identity and a logic channel identity, a downlink logic channel to adownlink transport channel corresponding to a MAC entity; and

perform the fourth mapping between the channels as follows:

when the fourth mapping is specifically a mapping between a transportchannel identity and a physical entity identity, mapping, according tothe mapping between the transport channel identity and the physicalentity identity, an uplink transport channel to an uplink physicalchannel corresponding to a physical entity; or

when the fourth mapping is specifically a mapping between a transportchannel identity and a cell identity, mapping, according to the mappingbetween the transport channel identity and the cell identity, an uplinktransport channel to an uplink physical channel corresponding to a cell;or

when the fourth mapping is specifically a mapping between a MAC entityidentity and a physical entity identity, mapping, according to themapping between the MAC entity identity and the physical entityidentity, an uplink transport channel corresponding to a MAC entity toan uplink physical channel corresponding to a physical entity; or

when the fourth mapping is specifically a mapping between a MAC entityidentity and a cell identity, mapping, according to the mapping betweenthe MAC entity identity and the cell identity, an uplink transportchannel corresponding to a MAC entity to an uplink physical channelcorresponding to a cell; or

when the fourth mapping is specifically a mapping between a transportchannel identity and a physical entity identity, mapping, according tothe mapping between the transport channel identity and the physicalentity identity, a downlink transport channel to a downlink physicalchannel corresponding to a physical entity; or

when the fourth mapping is specifically a mapping between a transportchannel identity and a cell identity, mapping, according to the mappingbetween the transport channel identity and the cell identity, an uplinktransport channel to an uplink physical channel corresponding to a cell;or when the fourth mapping is specifically a mapping between a MACentity identity and a physical entity identity, mapping, according tothe mapping between the MAC entity identity and the physical entityidentity, a downlink transport channel corresponding to a MAC entity toa downlink physical channel corresponding to a physical entity; or

when the fourth mapping is specifically a mapping between a MAC entityidentity and a cell identity, mapping, according to the mapping betweenthe MAC entity identity and the cell identity, a downlink transportchannel corresponding to a MAC entity to a downlink physical channelcorresponding to a cell.

Optionally, the processing module is specifically configured to: whennew data transmission is performed, schedule, according to the firstmapping and the second mapping, uplink data of a logic channel that ismapped to a physical entity/cell corresponding to an uplink grantresource.

Optionally, the processing module is specifically configured to:

when new data transmission is performed, schedule, according to thethird mapping and the fourth mapping, uplink data of a logic channelthat is mapped to a physical entity/cell corresponding to an uplinkgrant resource.

Optionally, the processing module is further configured to:

when the MAC layer configuration parameter further includes a MAClayer-related parameter corresponding to each set of mapping, and thereis one MAC entity, independently execute at least one MAC function ofthe following items: DRX, SPS, and HARQ according to the MAClayer-related parameter corresponding to each set of mapping and usingeach set of mapping as a unit; or

when the MAC layer configuration parameter further includes a MAClayer-related parameter corresponding to each set of mapping, and thereare at least two MAC entities, independently execute at least one MACfunction of the following items: DRX, SPS, and HARQ according to the MAClayer-related parameter corresponding to each MAC entity and using eachMAC entity as a unit, where

the MAC layer configuration parameter further includes a MAClayer-related parameter corresponding to each set of mapping, and theMAC layer-related parameter includes at least one of the followingitems: a DRX configuration parameter, an SPS configuration parameter,and HARQ retransmission times.

FIG. 10 is a schematic structural diagram of a device for schedulingmulti-flow transmission according to another embodiment of the presentapplication. The device may be an LTE base station, an LTE access node,an RNC, an eNodeB, and a D2D terminal, and the device includes adetermining module 101 and a sending module 102;

the determining module 101 is configured to determine a MAC layerconfiguration parameter corresponding to a MAC entity, where when thereis one MAC entity, the MAC layer configuration parameter includes atleast two sets of mappings, and the mapping includes a first mappingand/or a second mapping; or when there are at least two MAC entities, aMAC layer configuration parameter of each MAC entity includes a set ofmapping, and the mapping includes a third mapping and/or a fourthmapping, where

the first mapping is a mapping between a logic channel/radio bearer RBand a transport channel;

the second mapping is a mapping between a transport channel and acell/physical entity;

the third mapping is a mapping between a logic channel/radio bearer RBand a transport channel/each MAC entity; and

the fourth mapping is a mapping between a transport channel/each MACentity and a cell/physical entity; and

the sending module 102 is configured to send the MAC layer configurationparameter determined by the determining module to a terminal, so thatthe terminal executes a MAC layer function according to the MAC layerconfiguration parameter, and performs MAC layer data transmission.

Optionally, the determining module is specifically configured to, whenthere is one MAC entity, determine that the first mapping isspecifically a mapping between a logic channel identity and a transportchannel identity; or the first mapping is specifically a mapping betweenan RB identity and a transport channel identity; or the second mappingis specifically a mapping between a transport channel identity and aphysical entity identity; or the second mapping is specifically amapping between a transport channel identity and a cell identity; or

the determining module is specifically configured to, when there are atleast two MAC entities, determine that the third mapping is specificallya mapping between a logic channel identity and a transport channelidentity; or the third mapping is specifically a mapping between an RBidentity and a transport channel identity; or the third mapping isspecifically a mapping between a logic channel identity and a MAC entityidentity; or the third mapping is specifically a mapping between an RBidentity and a MAC entity identity; or the fourth mapping isspecifically a mapping between a transport channel identity and aphysical entity identity; or the fourth mapping is specifically amapping between a transport channel identity and a cell identity; or thefourth mapping is specifically a mapping between a MAC entity identityand a physical entity identity; or the fourth mapping is specifically amapping between a MAC entity identity and a cell identity.

Optionally, the MAC layer configuration parameter obtained by thedetermining module further includes a MAC layer-related parametercorresponding to each set of mapping, and the MAC layer-relatedparameter includes at least one of the following items: a discontinuousreception DRX configuration parameter, a semi-persistent schedule SPSconfiguration parameter, and hybrid automatic repeat request HARQretransmission times.

In this embodiment, by configuring at least two sets of mappings,different logic channels/RBs can be mapped to different transportchannels/MAC entities and/or cells/physical entities according todifferent sets of mappings, so as to satisfy a demand of a multi-flowtransmission scenario, thereby improving MAC layer transmissionefficiency.

Persons of ordinary skill in the art may understand that all or a partof the steps of the foregoing method embodiments may be implemented by aprogram instructing relevant hardware. The foregoing program may bestored in a computer readable storage medium. When the program runs, thesteps of the foregoing method embodiments are performed. The foregoingstorage medium includes various mediums capable of storing program code,such as a ROM, a RAM, a magnetic disk, or an optical disc.

Finally, it should be noted that the foregoing embodiments are merelyintended for describing the technical solutions of the presentapplication rather than limiting the present application. Although thepresent application is described in detail with reference to theforegoing embodiments, persons of ordinary skill in the art shouldunderstand that they may still make modifications to the technicalsolutions described in the foregoing embodiments, or make equivalentreplacements to some or all of the technical features thereof; however,these modifications or replacements do not make the essence ofcorresponding technical solutions depart from the scope of the technicalsolutions in the embodiments of the present application.

What is claimed is:
 1. A method for scheduling multi-flow transmission,the method comprising: receiving, from a base station by a terminalcorresponding to a first media access control (MAC) entity and a secondMAC entity, a first MAC layer configuration parameter corresponding tothe first MAC entity and a second MAC layer configuration parametercorresponding to the second MAC entity, wherein: the first MAC entitycorresponds to a macro cell of the base station, and the second MACentity corresponds to a cell of a secondary node, the first MAC layerconfiguration parameter and the second MAC layer configuration parametereach comprises a set of mapping and a MAC-layer related parametercorresponding to the set of mapping, and each set of mapping comprises amapping between any two or more of: a logic channel, a radio bearer(RB), a transmission channel, or each MAC entity; executing, by theterminal, the mapping corresponding to each MAC entity; andindependently executing, by the terminal, a MAC layer function based onthe MAC layer-related parameter corresponding to each MAC entity.
 2. Themethod according to claim 1, wherein each MAC layer-related parametercomprises at least one of the following items: a discontinuous reception(DRX) configuration parameter, a semi-persistent schedule configurationparameter, or a maximum number of hybrid automatic repeat request (HARQ)retransmissions.
 3. The method according to claim 2, wherein each MAClayer-related parameter comprises the DRX configuration parameter, thesemi-persistent schedule configuration parameter, and the maximum numberof HARQ retransmissions.
 4. The method according to claim 1, whereinexecuting the MAC layer function comprises: performing independentuplink scheduling on each MAC entity.
 5. The method according to claim1, in an uplink transmission, the method further comprising: when themapping is a mapping between a logic channel identity and a transmissionchannel identity, mapping an uplink logic channel to an uplinktransmission channel according to the mapping between the logic channelidentity and the transmission channel identity; or when the mapping is amapping between an RB identity and a transmission channel identity,mapping an uplink logic channel to an uplink transmission channelaccording to the mapping between the RB identity and the transmissionchannel identity and correspondence between the RB identity and a logicchannel identity; or when the mapping is a mapping between a logicchannel identity and a MAC entity identity, mapping, according to themapping between the logic channel identity and the MAC entity identity,an uplink logic channel to an uplink transmission channel correspondingto a MAC entity; or when the mapping is a mapping between an RB identityand a MAC entity identity, mapping, according to the mapping between theRB identity and the MAC entity identity and correspondence between theRB identity and a logic channel identity, an uplink logic channel to anuplink transmission channel corresponding to a MAC entity.
 6. The methodaccording to claim 1, in a downlink transmission, the method furthercomprising: when the mapping is a mapping between a logic channelidentity and a transmission channel identity, mapping a downlink logicchannel to a downlink transmission channel according to the mappingbetween the logic channel identity and the transmission channelidentity; or when the mapping is a mapping between an RB identity and atransmission channel identity, mapping a downlink logic channel to adownlink transmission channel according to the mapping between the RBidentity and the transmission channel identity and correspondencebetween the RB identity and a logic channel identity; or when themapping is a mapping between a logic channel identity and a MAC entityidentity, mapping, according to the mapping between the logic channelidentity and the MAC entity identity, a downlink logic channel to adownlink transmission channel corresponding to a MAC entity; or when themapping is a mapping between an RB identity and a MAC entity identity,mapping, according to the mapping between the RB identity and the MACentity identity and correspondence between the RB identity and a logicchannel identity, a downlink logic channel to a downlink transmissionchannel corresponding to a MAC entity.
 7. An apparatus, comprising: amemory storing program instructions; and at least one processor coupledto the memory, wherein when the program instructions stored in thememory are executed by the least one processor, the apparatuscorresponding to a first media access control (MAC) entity and a secondMAC entity is caused to perform the following: receiving, from a basestation, a first MAC layer configuration parameter corresponding to thefirst MAC entity and a second MAC layer configuration parametercorresponding to the second MAC entity, wherein: the first MAC entitycorresponds to a macro cell of the base station, and the second MACentity corresponds to a cell of a secondary node, the first MAC layerconfiguration parameter and the second MAC layer configuration parametereach comprises a set of mapping and a MAC-layer related parametercorresponding to the set of mapping, and each set of mapping comprises amapping between any two or more of: a logic channel, a radio bearer(RB), a transmission channel, or each MAC entity; executing the mappingcorresponding to each MAC entity; and independently executing a MAClayer function based on the MAC layer-related parameter corresponding toeach MAC entity.
 8. The apparatus according to claim 7, wherein each MAClayer-related parameter comprises at least one of the following items: adiscontinuous reception (DRX) configuration parameter, a semi-persistentschedule configuration parameter, or a maximum number of hybridautomatic repeat request (HARQ) retransmissions.
 9. The apparatusaccording to claim 8, wherein each MAC layer-related parameter comprisesthe DRX configuration parameter, the semi-persistent scheduleconfiguration parameter, and the maximum number of HARQ retransmissions.10. The apparatus according to claim 7, wherein the programinstructions, when executed by the at least one processor, further causethe apparatus to perform independent uplink scheduling on each MACentity.
 11. The apparatus according to claim 7, wherein the programinstructions, when executed by the at least one processor, in an uplinktransmission, further cause the apparatus to: when the mapping is amapping between a logic channel identity and a transmission channelidentity, map an uplink logic channel to an uplink transmission channelaccording to the mapping between the logic channel identity and thetransmission channel identity; or when the mapping is a mapping betweenan RB identity and a transmission channel identity, map an uplink logicchannel to an uplink transmission channel according to the mappingbetween the RB identity and the transmission channel identity andcorrespondence between the RB identity and a logic channel identity; orwhen the mapping is a mapping between a logic channel identity and a MACentity identity, map, according to the mapping between the logic channelidentity and the MAC entity identity, an uplink logic channel to anuplink transmission channel corresponding to a MAC entity; or when themapping is a mapping between an RB identity and a MAC entity identity,map, according to the mapping between the RB identity and the MAC entityidentity and correspondence between the RB identity and a logic channelidentity, an uplink logic channel to an uplink transmission channelcorresponding to a MAC entity.
 12. The apparatus according to claim 7,wherein the program instructions, when executed by the at least oneprocessor, in a downlink transmission, further cause the apparatus to:when the mapping is a mapping between a logic channel identity and atransmission channel identity, map a downlink logic channel to adownlink transmission channel according to the mapping between the logicchannel identity and the transmission channel identity; or when themapping is a mapping between an RB identity and a transmission channelidentity, map a downlink logic channel to a downlink transmissionchannel according to the mapping between the RB identity and thetransmission channel identity and correspondence between the RB identityand a logic channel identity; or when the mapping is a mapping between alogic channel identity and a MAC entity identity, map, according to themapping between the logic channel identity and the MAC entity identity,a downlink logic channel to a downlink transmission channelcorresponding to a MAC entity; or when the mapping is a mapping betweenan RB identity and a MAC entity identity, map, according to the mappingbetween the RB identity and the MAC entity identity and correspondencebetween the RB identity and a logic channel identity, a downlink logicchannel to a downlink transmission channel corresponding to a MACentity.
 13. An apparatus, comprising: a memory storing programinstructions; and at least one processor coupled to the memory, whereinwhen the program instructions stored in the memory are executed by theleast one processor, the apparatus is caused to perform the following:configuring, for a terminal, a first media access control (MAC) layerconfiguration parameter corresponding to a first MAC entity and a secondMAC layer configuration parameter corresponding to a second MAC entity,wherein: the first MAC entity corresponds to a macro cell of the basestation and the second MAC entity corresponds to a cell of a secondarynode, the first MAC layer configuration parameter and the second MAClayer configuration parameter each comprise a set of mapping and aMAC-layer related parameter corresponding to the set of mapping, andeach set of mapping comprises a mapping between any two or more of: alogic channel, a radio bearer (RB), a transmission channel, or each MACentity; sending the first and second MAC layer configuration parametersto the terminal for enabling the terminal to (i) execute the mappingcorresponding to each MAC entity, and (ii) independently execute a MAClayer function based on the MAC layer-related parameter corresponding toeach MAC entity.
 14. The apparatus according to claim 13, wherein eachMAC layer-related parameter comprises at least one of the followingitems: a discontinuous reception (DRX) configuration parameter, asemi-persistent schedule configuration parameter, or a maximum number ofhybrid automatic repeat request (HARQ) retransmissions.
 15. Theapparatus according to claim 14, wherein each MAC layer-relatedparameter comprises the DRX configuration parameter, the semi-persistentschedule configuration parameter, and the maximum number of HARQretransmissions.
 16. The apparatus according to claim 13, wherein: themapping is a mapping between a logic channel identity and a transmissionchannel identity; or a mapping between an RB identity and a transmissionchannel identity; or a mapping between a logic channel identity and aMAC entity identity; or a mapping between an RB identity and a MACentity identity.
 17. The apparatus according to claim 13, wherein: themapping is a mapping between a RB identity and a transmission channelidentity, and correspondence between the RB identity and a logic channelidentity; or a mapping between a RB identity and a MAC entity identityand correspondence between the RB identity and a logic channel identity.